ÅÉFile Areas - Area CommentâÉ ~ This is simply a one line description of the current file area. It's used for reports, description headers and so on. ÅÉFile Areas - Convert Files?âÉ ~ Earlier you specified a compression format to convert all files in this directory to. If you would rather not do compression conversion, specify "N" here. ÅÉFile Areas - Convert ToâÉ ~ Compressed files can be converted to many different formats. You may not care which format, but if you like to keep all files in the same format you can specify here which one. If any files are found not of the specified format they will be converted automatically. ÅÉFile Areas - Description FileâÉ ~ This is the file that contains the descriptions for this area. This would be the DIR file associated for the area. ÅÉFile Areas - Description OptionâÉ ~ Compressed files usually contain a FILE_ID.DIZ, which is a text file that contains the file's description. Users usually add descriptions manually when they upload. .TIC files usually have the description within them. Usually. This option covers the unusual: ~ Never - Descriptions are never added, and assumed supplied.` Always - Descriptions are always imported from the FILE_ID.DIZ.` Needed - A description is added if missing from any of the above. ÅÉFile Areas - Dupe Check?âÉ ~ If this option is set to "Y", the directory and description file will be checked for duplicate files. If duplicates are found, one file and description will be left, and the other killed. ÅÉFile Areas - File Base NameâÉ ~ This is the name of the Base Runner File Base for this area. This name follows all DOS filename restrictions, and can be no longer than 8 characters. The extension is added automatically. ÅÉFile Areas - File DirectoryâÉ ~ This is the sub-directory where the files for this area are stored. Do not include a trailing backslash. You will be prompted to create the directory if it doesn't exist. ÅÉFile Areas - ASCII Filter?âÉ ~ Sometimes descriptions through file echos or uploads can have upper ASCII characters in them. These are characters such as smooth lines and boxes. If you want these converted to lower ASCII, specify "Y" here. For examle, if a description reads: ~ ÅÉ ■ Base Runner ■ File Base Processor ~ âÉ After it has been filtered, it will read: ~ ÅÉ * Base Runner * File Base Processor ` ÅÉFile Areas - Echo FoldersâÉ ~ Folders are a way of organizing your file areas. You must define at least one folder in order to configure file echos. ~ A folder is used to identify groups of areas with some similarity. For example, say you have file areas in different conferences or file groups. You could define different folders for each conference or file group. Or, you can define echo or non-echo areas. ~ Folders are used by BRConfig to make global changes easier. Say you need to change certain options for a group of areas such as auto echo or processing options. In area configuration you can specify which group to make global changes to. Folders are also used for access restrictions to file echos for any downlinks you might have. If you're still a bit foggy, define one group and then have a look through file area configuration. ÅÉFile Areas - Description File FootersâÉ ~ File area listings can also have a footer at the end of the listing. They work in the same manner as the headers do. Refer to the main documentation for details on headers and footers. ÅÉFile Areas - Description File HeaderâÉ ~ Description files can have a header inserted at the top of each listing. You can construct a header with any text, ANSI or PCBoard color code editor. Within it you can place symbols that represent certain file area statistics such as total files, total bytes, etc. Refer to the main documentation for instructions on how to construct directory headers and what symbols are available. ÅÉFile Areas - Original Dates?âÉ ~ If set to "Y", files moved and/or uploaded to this area will retain their original date and time. Otherwise, the date and time fo the file will be reset to the current date and time. This can come in handy for new file areas where you want new files treated as new. For example, if you set your new file area to move after 30 days, and you upload a file to that area that's a year old, it will move out of the new file area on the next process. ÅÉFile Areas - Sort ByâÉ ~ Every time a filebase is updated, it is sorted. This specifies how you want the description file sorted. That is either by filename or date. ÅÉFile Areas - Zip CommentsâÉ ~ Many compression utilities allow you to add a comment at the top of the file, which is displayed when the compressed file is viewed or decompressed. This is the line that will be added as a comment. If this line is started with a "!", it is assumed to be a valid filename, and the contents of that file are used as the comment. For example, if you specified a line like: ~ From CompuData (xxx)-xxx-xxxx ~ That text will be added as is. If you specified: ~ %C:\COMPDATA\ZCOMMENT.TXT ~ The contents of ZCOMMENT.TXT will be placed within the compressed file as a comment. If a compression format does not support embedded comments, this option will not be used. ÅÉFile Areas - Sort OrderâÉ ~ File areas can be sorted by filename or date, and this option specifies whether the area is sorted in ascending or descending order. ÅÉFile Areas - Hatch into which Echo ~ âÉThis tells Base Runner which echo you wish adoptions to go to when new files come in. This is only the base, it does not actually activate the feature. You have to have auto hatching active first. ÅÉFile Areas - Virus scan?âÉ ~ Any new files added to the system by user upload, sysop upload or file echo will be scanned for viruses using the scanner supplied in global configuration if this option is set to "Y". ÅÉFile Areas - Delete From Compressed FilesâÉ ~ Here you can specify any filename to be removed from all compressed files entering this area. If there is more than one file to be removed, placing a % at the beginning of the filename specifies a text file sith a list of filenames to remove. So if you add the entry "BBSAD.TXT", that file will be removed from any compressed files. If it's "%BADLIST.TXT", this is assumed to contain a list of filenames to remove. ~ Some compression utilities take such as file as a command line parameter and the whole list is removed in one call to the extraction utility. Note that not all do, like LZH. In this case the update utility will be called for as many filenames exist in the file specified and prefixed with a %. ÅÉFile Areas - Maximum Files to KeepâÉ ~ If this option is 0, the funtion is disabled. Otherwise, it indicates the maximum number of files to keep in this area. Any new files entering cause DynaBase to delete the oldest file in the area to maintain the number specified here. Use this feature with caution as it will delete files. ÅÉFile Areas - Delete Files Older ThanâÉ ~ If 0, this function is disabled. Otherwise it specifies the number of days old files will be deleted by. For example, if you specified 365 here, files older than one year will be deleted. This is handy for maintaing level disk space usage but cation should be used. ÅÉFile Areas - Perform Deletions?âÉ ~ Base Runner can perform a deletion function, where it will check the filebase against the files in its associated directory and remove any filebase entries that have had their associated file deleted for whatever reason. This operation in cooperation with the next option (Adoptions) ensures a file area is always perfectly up to date. ÅÉFile Areas - Perform Adoptions?âÉ ~ This option is the opposite of Deletions. It compares a filebase with its associated directory and looks for files that there are no filebase entries for (Orphans). These files are adopted into the filebase via FILE_ID.DIZ extraction and so on. ÅÉWide Area Duplicate Detection?âÉ ~ This will tell Base Runner whether or not it should check all areas for duplicates rather than just this one. This is to accomodate the possible hatching of files into more than one area. If you set this to "Y" then you are telling Base Runner to check all areas in which case even if the file has come into another area, it will be found to be a dupe. ÅÉMain Menu - System InformationâÉ ~ This option takes you to a secondary menu where most of the main system defaults reside. These are, global and path information, system identification, compression commands and network addresses. ÅÉFile FoldersâÉ ~ The File Folder section allows you to assign different groups of areas. Many of Base Runners functions can be maniplated easier when they are performed on groups of areas with something in common. More detail is included within the File Folder section. ÅÉNode InformationâÉ ~ When utilizing File Echoes, Node Information holds data in reference to each node within a Fido type network that you communicate with. If you do not plan on using File Echoes, this section can be ignored. ÅÉ(BBS)File Areas ~ âÉThis section allows you to define any or all of the file areas you carry on your BBS. Regardless of whether or not you carry file echoes, this section is required as the heart of configuration. ÅÉ(TICS)File EchoesâÉ ~ If you are a member of a Fido type network and with to participate in File echoes, information pertaining to each echo area you carry is configured here. Note that you MUST have at least one file area defined in order to carry a file echo from within Base Runner ÅÉFile RequestingâÉ ~ Here you may tell Base Runner about your file requesting capabilities. A few toggles and paths are all that it contains, but are VERY important to the function of Base Runner. ÅÉExport DataâÉ ~ Allows you to export certain system information to text files or printers. ÅÉRequesting System ~ âÉThis is the file requesting system for your users. If you run a PCB system(sorry, door only supports PCB at this time), you can offer other systems file areas to your users. They can be flagged for download just as they would if the user was local except that the user waits for the requested file(s) to come in at which time they may download. ÅÉExit to DOSâÉ ~ This selection will exit BRConfig and return you to the DOS prompt. ÅÉGlobal OptionsâÉ ~ This section contains options that cover the behaviour of your system as a whole such as your BBS name and general system behavior. ÅÉCompression CommandsâÉ ~ Base Runner supports a number of file compression formats such as ZIP, LZH, etc. The commands used to add to or extract compressed files are specified here. ÅÉSystem AddressesâÉ ~ This section contains the Fido type addresses that you may have within a Fido type network. These are also known as AKA's. If you do not plan on carrying File Echoes you can ignore this section. ÅÉWelcome to Base Runner!âÉ ~ You have found the main configuration program for Base Runner. A File Area called "BAD_FILES" has already been created for you. This area is used for files that duplicate others, or fail security checks. You will need to tailor this area to your needs before running Base Runner. ~ However, first start from the top of the menu and work your way down. Help can be aquired at any menu or prompt by pressing F1. It is highly recommended you keep the documentation handy to gain the best understanding of how Base Runner operates. ÅÉOrigin LinesâÉ ~ This option allows you to specify up to 10 origin lines. These are used on the bottom of messages and reports. Not in use. ÅÉSystem Information - File List OptionâÉ ~ This is the path and name of the master file list. If this field is left blank, no file list will be generated. Please do NOT include an extension. The default of ZIP is only supported at this time. Alot of sysops like to use their BBS name as part of the list name, eg... D:\PCB\BASERUN\SALTAIR . For more information, see the option under Global Options or consult the documentation. ~ ÅÉSystem Information - AKA'sâÉ ~ If you are a member of a Fido type network, you should have been assigned a node number by your network host. Here, you list any addresses (or AKA's) you have starting with your main address first. Each address can be in a 4 dimensional format; ie. 1:229/428.2. At the very least, a net/node number is required. Point and Zone numbers are optional. ÅÉSystem Information - BBS NameâÉ ~ This is the name of your BBS, such as "Fred's Communications". It is used throughout Base Runner in a variety of ways such as reports and so on. ÅÉSystem Information - LocationâÉ ~ This is your location such as Oshawa ON Canada or PrinceVille HA USA. It is also used around the system for reports and so on. ÅÉSystem Information - Sysop NameâÉ ~ I know this may be a hard concept for some to grasp, but this is your name. If you can' remember it, check your wallet for your birth certificate or ask your mother. ÅÉSystem Information - Compression InfoâÉ ~ Base Runner supports a number of compression formats. There are 3 fields per format and up to 10 compression formats may be specified. The first field specifies the extension, the other two are the DOS commands and command line switches used for compression and decompression. ~ Base Runner uses signature indentification on Zip, Arc, Lzh, Pak, Zoo and Arj archives. This means it knows what kind of compression is used on a given file by the signature within the file itself. ~ You can also define your own. In such cases, Base Runner will identify the type of compression by the extension if it doesn't recognize the signature. Also, some compression utilities handle their command line parameters differently. The above formats all accept the filename of the compressed file as the first parameter. However, not all do. If this is the case with a compression format not internally supported, a %N can be placed anywhere in the command line to represent the filename. For example, if you were to use the utility MYCOMP.EXE, you could specify the command line for extraction like so: ~ MYCOMP -X -D %N ~ When Base Runner processes the file TEST.MCP it would construct the extraction command above like so: ~ MYCOMP -X -D TEST.MCP ~ More detail is supplied in the main documentation on user defineable compression formats. ÅÉSystem Info - Inbound DirectoryâÉ ~ This is the path to where Base Runner can find incoming file echo files. Since Base Runner is designed to work with Fido type file echoing systems, one or more .TIC files are expected as well as the files themselves. This is usually the inbound directory specified in your front end mailer's setup. ÅÉSystem Information - Outbound DirectoryâÉ ~ This is where Base Runner will place outbound files. That is, files that are being hatched or downlinked into a file echo. It is HIGHLY recommended that this path remain for the use of Base Runner only. ÅÉSystem Information - Phone NumbersâÉ ~ Here you enter the phone number for your BBS. It's used around the system in reports and so on. ÅÉSystem Information - Pass Through DirectoryâÉ ~ A file echo that is specified as "Pass-Thru" means that files from an echo enter your system and are sent out to any systems below you, but are deleted once sent and not kept on your system. ~ The pass-thru directory is used for two things. One is as described above. The other is, regardless if an echo area is specified as pass-thru, outbound files and .TICs are copied here and remain until they are sent. If you downlink file echoes to any other systems, even if none of them are specified as pass-thru, Base Runner will use this directory as a holding area until the outbound files are delivered. ÅÉSystem Information - Netmail DirectoryâÉ ~ Base Runner sends and receives information and files via netmail attach messages. This is the directory where netmail messages are stored. Both the File Manager and the file echo processor use this directory. It would be the same netmail directory as your front end mailer uses. ÅÉSystem Information - Virus CheckerâÉ ~ This is the name of your virus checker, and any command line parameters. In order for Base Runner to function properly, your virus checker should exit with an errorlevel of 0 on success. ÅÉSystem Information - File Base PathâÉ ~ Base Runner stores all information about the files on your system in file databases. This directory specifies where Base Runner can find these databases. We recommend it be a directory on its own such as C:\DBASE\FBASE so that your main Base Runner directory doesn't get cluttered. ÅÉSystem Information - Move to Bad?âÉ ~ If you specify "Y" here, Base Runner will move any Bad files to the file area defined as "BAD_FILES". BRConfig creates this area for your the first time you run it, but if it doesn't exist, it will leave the file along. This may be anything from files that aren't recognized by a valid node number(and node auto-add is off) or if a file fails during importing for any reason(virus, CRC fail,trashcan file found,duplicate etc). If the file is not specified to be moved to the bad area and any of the above conditions are not met, then the file is ignored so that you may manually deal with it. The TIC file(if this file is echoed in) is also left alone. ÅÉSystem Information - Dupe LimitâÉ ~ Base Runner maintains a duplicate file database under the filename BRDUPE.DAT. Each time a file enters the system its CRC is calculated and stored in dupe base. If the same file tries to enter the system its calculated CRC is compared against each entry in the dupe base. If it matches, it is considered a duplicate file and acted upon as per the above option (Dupe Option). ~ After a few thousand files, the dupe base can grow and the time it takes to search it can increase. This value determines the maximum number of entries maintained in the dupe base. If you specify 1000, the last 1000 files to enter the system are compared to any new files arriving. ~ The dupe base is packed automatically at the end of every Base Runner process or through BRUtil. You can change this value at any time. ÅÉSystem Information - Log File LocationâÉ ~ This is the path and name of the log file that Base Runner will generate as it runs. You can specify a central log file, but log file report generators may not properly read what Base Runner writes to the log file. Therefore it's best that Base Runner maintain its own individual log. ÅÉSystem Information - Uplink ListâÉ ~ When you are hooked into a file echo system and feeding files to other systems, you may or may not have an uplink. That is, the system you get your files from. Base Runner supports what is known as Areafix Forwarding. If one of your downlinks requests to be hooked up to an area which is not defined in configuration, Base Runner will search the filename you specify here for the area name requested. If found, a File Manager request is generated for your uplink to connect the area. ~ The file spceified here is expected to be an ASCII text file, one area per line with the areaname being the first word on each line. An example list may look like so: ~ PCB-DOORS PCBoard Doors` NODELIST FidoNet Nodelists` PDNCEE PDN C Echo` ~ The file can be any length and the description is optional. Note that the larger the file is, the longer it will take to search it. No Help Available. No Help Available. No Help Available. ÅÉFile FoldersâÉ ~ File Folders apply to both file areas and file echoes. They are used as a way of referencing areas with something in common. How you use these folders and what you call them is up to you. ~ For File Areas, suppose you have file areas both on hard disk and CDROM. You can define a folder for each of these. In file area configuration you specify which areas belong to which folder. This makes some things easier such as global changes to your file area configuration without applying those selected changes to all areas. There is one more consideration when dealing with file folders. If you are involved in file requesting, you can limit the requesting nodes access to certain folders if you like. ~ File Echoes use them the same way, but with one added difference. In node configuration, when you configure each system you may supply files to, you select which folders each node has access to. This way you can limit certain echo areas for different nodes. This applies to echoing files, not requesting, files, please do not mix up the two. ~ You must define at least one folder. If you're confused, define one folder and note the effect it has when you are configuring your file areas or echoes. ÅÉNode Information - System AddressâÉ ~ This field specifies a Fido type 4 dimensional address such as 1:229/428.3. The point number is optional. This will be the address used for netmail messages. ÅÉNode Information - Sysop NameâÉ ~ This is the name of the sysop at the above node address. ÅÉNode Information - File Manager PasswordâÉ ~ In order for a system which you may be feeding files to connect or disconnect echo areas using the File Manager, each node will need a password that either you or they supply. Without this password any requests will be ignored. ÅÉNode Information - File FoldersâÉ ~ This option allows you to choose one or more previously defined file folders to which each node has access to. You may not want all nodes to access all the echo areas you carry. What echo areas belong to which file folder is specified in file echo configuration. ~ When presented with a list of folders, move the highlight to the folder(s) you which to select. The space bar will toggle each folder on or off. Note that folder changes cannot be made from remote using the File Manager. ÅÉNode Information - Allow Request Forwarding?âÉ ~ When a node you are feeding file echoes to requests and area that is not defined in file echo configuration, a specified uplink list is checked for the area. If it is found there, a File Manager request is generated and sent to your uplink. ~ This option tells Base Runner NOT to perform this process for this node. Some uplinks don't allow it or you may simply want to stop certain nodes from performing this action. ÅÉNode Information - Attach Msg/AreaMgr Attribute ~ âÉ This speifies how netmail messages to this node should be sent. The options available are: ~ ÅÉ None - âÉNone - Based on your mailer's routing` ÅÉ Crash - âÉSend Files/Messages right away, directly` ÅÉ Hold - âÉHold Files/Messages for pickup.` ÅÉ Direct - âÉDirect but not Crash or Hold.` ÅÉ Crash Direct - âÉCrash and Direct.` ÅÉ Hold Direct - âÉHold and Direct.` ~ âÉ Some of your nodes may be listed as private, or you may have events defined to send files at a specific time of day. ÅÉFile Echo Configuration - Area NameâÉ ~ Each file echo you define MUST have a unique area name. This name is usually predefined by your uplink, which is usually supplied in a text listing of some sort. The area name can be up to 30 characters lone and must be unique. Note also that this area name can duplicate an Echo Area name. ÅÉFile Echo Configuration - Area CommentâÉ ~ This is simply a one line comment used to describe this area. It is used throughout Base Runner in various areas such as the File Manager. ÅÉFile Echo Configuration - File FolderâÉ ~ Here you specify to which file folder this area belongs to. You can have up to 30 file folders defined but you may choose only one here. See the help under file folder configuration for more info. Not sure what this does. <shrug> ÅÉFile Echo Configuration - Initial File AreaâÉ ~ When one or more files enter your system through this file echo, Base Runner needs to know which file AREA to initially place it in. For example, you could have certain file echoes place their files in your new upload area initially and have automatic file movement move them elsewhere later on. ÅÉFile Echo Configuration - File Area OwnershipâÉ ~ This option specifies which file AREA owns files brought into this echo. Remember that files can exist in file AREAS that they are not owned by. For example, for a givien file ECHO, you can have its files INITIALLY placed in a new upload area. However, the files can be OWNED by some other area. Where the files go from the initial area depends on how the initial area is configured. ÅÉFile Echo Configuration - AKA'sâÉ ~ In System Information, you configured which AKA's your system is "also known by". A list of those AKA's (Fido addresses) is presented, and you can choose one or more by moving the highlight and pressing the spacebar. The AKA you choose will be used in both outbound netmail and TIC files. ÅÉFile Echo Configuration - DownlinksâÉ ~ Here you specify a list of nodes or downlinks that will receive the files passing through this echo area. On the left side of the screen is a window that contains the list of nodes you previously defined in Node Configuration. You can scroll through this list with the up/down arrow keys or PGUP/PGDN. The spacebar will add or remove the highlighted node number in the window on the right. ~ Note that this list can contain your uplink if this is a two way echo. Entries can also be added or removed automaticly via the File Manager. ÅÉFile Echo Configuration - Pass Thru Area?âÉ ~ If you define this area to be pass-thru, this means that files that enter your system via this echo are not imported into your file bases. If this area has downlinks, the inbound files are copied to the passthru directory specified in global options and deleted once sent. ÅÉFile Echo Configuration - Include in Reports?âÉ ~ This tells us whether or not you want this area included in reports. ÅÉProcess File Manager RequestsâÉ ~ Should we run the File Manager so that downlinks may request new areas, remove areas, change their password etc. All these things are handled by the file manager so if you have downlinks, set this to "Y". ÅÉFile Echo Configuration - List This Area?âÉ ~ When a remote node requests a list of areas via the file manager, this option specifies whether or not this area is listed in that report. You may want some private areas available but not listed. ÅÉFile Echo Configuration - Enable Security?âÉ ~ This enables strict checking of inbound files. If inbound files are not addressed to you they will be considered "BAD" and processed as a bad file if this option is set to "Y". Otherwise, inbound files are processed as usual regardless of the destination address. ÅÉFile Echo Configuration - Echo This Area?âÉ ~ This option is included as a fail safe. If you specify "N" here, NO files will echoed back to your uplink. It is treated as a receive only area. However, if there are any downlinks configured for this area they are fed outbound files as usual. ÅÉFile Echo Configuration - Auto Echo Area?âÉ ~ Auto echo is a process by which the Orphan Adoption process of Base Runner automaticly hatches any new files copied into the directory for this echo area. This option will enable or disable this feature. See the main documentation for more details on Auto Echo. ÅÉFile Echo Configuration - Auto Add This Area?âÉ ~ If set to "Y", this area will be added to all nodes that have access to it via the specified folders for each node. Nodes are added automaticly at processing time. ÅÉFile Echo Configuration - Keep Receipts?âÉ ~ If you support File Manager forwarding for this area, the receipts received from your uplink will be retained. Otherwise they will be deleted. ÅÉFile Echo Configuration - Keep Requests?âÉ ~ If you support File Manager forwarding for this area, the requests sent to your uplink will be retained. Otherwise they will be deleted. ÅÉFile Echo Configuration - Delete TIC Files?âÉ ~ While processing inbound files, this instructs Base Runner to either keep or delete the TIC files. This option is almost always set to "Y". Otherwise Base Runner will repeatedly attempt to re=process the same TIC files. ÅÉFile Echo Configuration - Delete Attach Files?âÉ ~ While processing inbound files, this instructs Base Runner to either keep or delete the inbound files. This option is almost always set to "Y". Otherwise Base Runner will leave the files in the inbound directory and copy them to their destinations. ÅÉFile Area Configuration - âÉ ~ This option is simply a description of this file area like "C++ Programming". It will appear in various places around the Base Runner system. ÅÉFile Area Configuration - Destination DirectoryâÉ ~ This is the drive and sub-directory where the files for this area are stored. It can be on hard disk or CDROM. ÅÉFile Area Configuration - Description FileâÉ ~ This is the drive, path and filename of the PCBoard DIR file that will hold the text listing for this area that a user would see. It is regenerated automaticly by Base Runner any time changes are made to the associated file database. ÅÉFile Area Configuration - Uploaded By:âÉ ~ What you enter here will be added to the end of the descriptions of files that enter the system via this area. A "%A" can be used here to represent certain information. For example, if you entered the follwing here: ~ Uploaded by: %A` ~ The "%A" would be replaced with the following: ~ Entry Method Result` ------------------------ --------------------------------` User Upload Uploaded By: Steve Tupy` File Echo Inbound Uploaded By: NODELIST` File Adoption Uploaded By: Base Runner` Local Upload Uploaded By: Sysop ~ The "%A" is not required. You could specify any text here and Base Runner will append it to the description. ÅÉFile Area Configuration - Include FilesâÉ ~ When a compressed file enters the Base Runner system through this area, you can have it add one or more files to the compressed file such as BBS ads or whatever. You can specify a filename 2 ways: ~ C:\DBASE\BBSAD.TXT or...` !C:\DBASE\ADDFILES.TXT ~ Just specifying one file like the first line above will add that file directly to any compressed files. The second line specifies a text file that contains a list of files to add. It can contain as many files as you like, one per line. Each of the files listed in the text file prefixed with a "!" will be added to compressed files in this area. ÅÉFile Area Configuration - Zip CommentâÉ ~ Some compression utilities such as ZIP give you the ability to add a comment to a compressed file. Specifying a line of text here, like "Joe's BBS - 555-5555" will use that as the comment. If you specify a valid text filename here the contents of the file will be used as the comment. Base RUnner will check for the existence of this field as a valid file and if the file cannot be found (perhaps it's text) it assumes it's text and uses it as the comment. ÅÉFile Area Configuration - Move To AreaâÉ ~ This option specifies what file area files in THIS area will be moved to. You can select any other file area defined in configuration. If you select "NOWHERE", files in this area will stay in this area. If you select "HOME", files will be moved to the file area that OWNS the file. See the field "Days Old" for movement frequency. ÅÉFile Area Configuration - Initial AreaâÉ ~ This option specifies the file area that files uploaded to THIS area will be initially placed. Files uploaded to this area will be OWNED by this area but can be initially placed in another area. Assuming that other area is configured for automatic file movement, this area's files will make it here (HOME) eventually. If you specify THIS area as the initial area for uploads, uploaded files will arrive here and stay here. ÅÉFile Area Configuration - Days OldâÉ ~ This specifies how old a file is before it is automaticly moved to another area. If you specify 30, after each file is 30 days old it will be moved to whatever area you specify in the Move To option. ÅÉFile Area Configuration - Delete by AgeâÉ ~ If you specify 0 here, files will be left alone. If you were to specify say, 90 here, files older than 90 days are automaticly DELETED with no questions asked. ÅÉFile Area Configuration - Maximum FilesâÉ ~ If you specify 0 here, files will be left alone. If you were to specify say, 100 here, this area will never hold more than 100 files. If a new file enters this area, the oldest file is DELETED. ÅÉFile Area Configuration - Convert Files ToâÉ ~ This specifies the compression format to convert files entering this area to. it may be any of the types defined in System Information/Compression. ÅÉFile Area Configuration - Virus ScannerâÉ ~ This is the command to execute your virus scanner, eg. SCAN.EXE. It should be one that returns a 0 errorlevel on success ÅÉFile Area Configuration - Keep Original File Dates?âÉ ~ When a file enters this area, it can either retain the original file date or be changed to today's date. ÅÉFile Area Configuration - Use CRC Updating?âÉ ~ When a file enters the system it's CRC value is stored. This option specifies that this area should have ALL CRC values recalculated and the associated file base record updated with a new description etc. The use of this function may be arare, as it would take up considerable time to check each file at every process. A manual operation of this sort can be performed using the BRUtil utility. ÅÉFile Area Configuration - Is This a CDROM Area?âÉ ~ If the files associated with this area are on a CDROM or other read only media, specify "Y" here. This will instruct Base Runner to treat the area a bit differently, like not trying to move files to it. ÅÉFile Area Configuration - Perform Deletion Check?âÉ ~ Base Runner can check to see if a file in this area's database doesn't exist on disk any longer. This ensures that missing files are kept track of. It's checked at each process, unless you specify "N" here. ÅÉFile Area Configuration - Perform Orphan Adoptions?âÉ ~ Files on disk but not in the database are referred to as Orphans. If you specify "Y" here, Base Runner will check the area for orphans and adopt them; adding the description and so on the file base. ÅÉPaths/FilesâÉ ~ This section contains information relating to your overall system configuration. This includes things like paths to where different files are stored and options that affect the system as a whole. ÅÉSystem Information - Headers DirectoryâÉ ~ Base Runner has the ability to create headers and footers for each file area listing generated for your BBS. The headers and footers generated by Base Runner are stored in this directory. For example, PCBoard uses individual files for the headers and footers . In this case, this directory is unused. ÅÉSystem Information - Work DirectoryâÉ ~ This directory is used by Base Runner for a number of reasons such as compression conversion. It should be a directory that no other program has access to as Base Runner can delete and copy files to and from this directory at any time. Also, please note that there must be NO directories below this one on your hard drive. The reason for this is that Base Runner will extract full pathnames from archives creating the necessary sub directories as they become available in the archive. When we are done, all these sub directories are then cleaned up and removed. When this happens, Base Runner does not know which directories are your regular directories and which ones were just extracted from the archive. Also, Base Runner uses all sub directories for archive conversion, using the full pathnames to properly recreate the archives original sub directories. This will cause confusion unless this work directory is an end directory on the tree. ÅÉSystem Information - Downlink OptionâÉ ~ Fido filebone echo areas distribute files to thousands of systems around the world. Think of the junk any given file would accumulate if each system a file passed through added a BBS ad file. This option dictates whether or not a file passing through your system should be unchanged when sent to your downlinks. ~ If you specify "Y" here, files downlinked by your system to other systems will be done so UNCHANGED. This procedure is HIGHLY recommended for (inter)national file echoes. Before Base Runner does any processing on an inbound file it copies it to your outbound directory first, ensuring no changes will be made to the file. (providing it is to be downlinked) This causes two copies of the file to exist on your system; one for downlink which is deleted once sent, and one processed into your system. ~ If you specify "N" here, the file is processed as per your configuration (eg. Zip convert, comments, etc) and downlinked as normal. This ensures only one copy of the file remains on your system at a time. Main documentaion covers this issue in much more detail. ÅÉSystem Information - Time ZoneâÉ ~ Here you specify the time zone you are currenty in such as GMT or EST. I know, "What's the point?". My sentiments exactly but that's the standard. Following is a list of valid time zones world wide: ~ ÅÉSystem Information - Network RetriesâÉ ~ If you run a multi-node system via a Local Area Network Base Runner has to worry about file sharing when two or more nodes are trying to access the same file. If a file is unavailable to Base Runner it will try opening the file a repeated number of times. This value determines how many times Base Runner will try opening a file if it's in use by another node. Specifying 0 here tells Base Runner to keep trying until hell freezes over if nessecary. ÅÉSystem Information - Network Retry DelayâÉ ~ The above option (retries) specifies how many times Base Runner will attempt to open a file locked by another node. This option specifies how long between retries it will wait. ÅÉSystem Information - Origin LinesâÉ ~ Appended to certain reports and messages are optional origin lines. This is a single line of text that says something about your system. Pre-pended to this line is the string " * Origin:" so for example, if you added the line: ~ ÅÉCompuData Systems, Oshawa ON - 905-xxx-xxxxïÉ ~ The resulting line in a given message or report would look like so: ~ ÅÉ* Origin: CompuData Systems, Oshawa ON - 905-xxx-xxxxïÉ ~ You can specify up to 10 origin lines up to 65 characters in length. Which line to use is specified in File Echo Configuration. ÅÉSystem Information - Master File List TypeâÉ ~ Most BBS's offer a master file list. That is, a master list of all files available on your system. Most BBS softwares offer this feature but one usually ends up with a 4 meg text file. What the HELL is anybody going to do with a 4 meg text file? ~ Base Runner offers two options for a master file list. One is the standard text file and the other is the Base Runner File Base itself. ~ If you specify "N" here, you will get a compressed zip in the name specified that will have all the DIR files(or FILES.BBS) in it as well as a control file which is just an areas listing. This control file is similar to the one used in the request system. If you specify "Y" here, Base Runner will generate a master file list comprised of your original file bases, a small config file and a freeware viewer for users to download and easily browse your file list. Either of these will be compressed and placed in the path specified in the Files/Paths section of System Information. More detail on the master file list function can be found in the main documentation. (which BTW, is NOT a 4 meg text file).~ ÅÉBRutil - Main Command Summary ~ ÅÉPack FileBases - âÉBRutil will go through all your file areas and take out all the "holes", spaces in the base where deleted records used to be. This feature is in this program as it was slowing the main program down to a crawl and was not needed every single time the program was run. ~ ÅÉBuild Indexes - âÉThis will prompt BRutil to regenerate all your file areas index files, if for some reason they become corrupt or you want to "clean" them up. ~ ÅÉDupes - âÉBRutil will check for duplicate files found WITHIN a base and keep only the newest entry according to the files date. All others will be abandoned permanently. ~ ÅÉDupe Trim - âÉInstead of having Base Runner go through this process each time, we put it in this program. It will trim down your duplicate database to the number specified in BrConfig. ~ ÅÉNotify - âÉWhen this is executed, BRutil will generate a notify list or a list of all available areas to that particular node. You will be prompted for a file and an area for the list. A netmail attach is created to the specified node with a list. ~ ÅÉHatch - âÉHatching is a means to send a file out to all the other nodes included in that areas list and to send them a .TIC file with your systems info in it, info about the file etc. You will be prompted for the file to hatch and the area to hatch it to . ~ ÅÉSend - âÉSending a file is similar to hatching except that you do not send the file to all nodes for a particular area. This is only for a dos file you do not have in a filebase, but wish to send to just ONE node with only a file attach but nothing else. ~ ÅÉInit Bases - âÉThis should only be run once or subsequently if you intend to add areas and adopt them from PCB. This will build complete new filebases from your PCB DIR files with CRC checking, descriptions, file ids etc. ~ ÅÉBuild CRC - âÉThis will go through all your areas and build a new duplicate database with only the CRC's from your existing system. If you wish to retain the offline files info so that you will not have more dupes coming in do not use this as it will delete the existing base and start from scratch. ~ ÅÉClean Nokill - âÉClears all No kill markers in the filebases allowing them to be moved around and processed regularily. When a file is marked nokill, nothing is done to it ever. ~ ÅÉAuto Unlinking - âÉAutomatically takes the area out but not out of your config. It merely disconnects this area from your uplink for this area. If you have no uplinks(in other words, you are the source for this area) for this area, it will never be unlinked. ~ ÅÉDir Writes - âÉPerforms Filebase generation. This is the DIR file or FILES.BBS file for your BBS. You may choose ALL or Select to pick only the areas you wish to generate. ~ ÅÉExit to Dos - âÉEsc or the right mouse button will do the same. This ends your session and drops you to DOS. ÅÉNotify Single Node? ~ âÉThis tells BRutil that you want to notify only one node. You will be prompted for the node number. You have to use the list provided as you cannot notify a node that is not connected to you. ÅÉNotify All Nodes? ~ âÉBy default when this is selected, there is no more prompting, it jumps right into generating messages for all your connected nodes. A file attach with the particular nodes status is created for each of the nodes in your list. ÅÉFileName to Send? ~ âÉThis is a fully qualified path and name of a dos file you wish to send out. Please remember that if you run a network and you are trying to send a file from a drive that is not available to the mailer nodes machine, it will not succesfully send the file as the path provided may be valid to the machine that generated the request, but not the machine that will end up sending the file. ÅÉNode to Send File To? ~ âÉThis is the node number of the node you wish a copy of this file to go to. An attach message is created in your netmail directory so that your mailer will know to send it out. You specify the netmail directory in BRCONFIG.EXE @15,0Select an Area to Hatch To ~ âÉThis is a list of available echo areas you may hatch this file into. Select the one you wish this file to be hatched to at which time BRutil will go through your list of nodes that take that area off of you and they will each recieve a copy of that file along with the appropriate .TIC file so they may process it into their system as well. ÅÉEdit FileName ~ âÉHere you may change the filename for this file. The file on disk is also renamed after you have finished editing. Remember you may abort the changes when you are finished editing as Fbedit will prompt you to save the changes. ÅÉMain Editing Screen Command List ~ F1 - âÉThis Help Screen. ~ ÅÉAlt A - âÉAdd as a file id file. This will take the existing description you have typed in and add it to the archive as a FILE_ID.DIZ file. This way you have a two way file id support system. ~ ÅÉAlt B - âÉAbandons the currently selected file. This will delete the database record but NOT the file on disk. ~ ÅÉAlt C - âÉMark for Copy. If you have already selected files using the spacebar, BRedit will prompt you whether you would like to mark ALL selected files for copy. Press F1 at that prompt for more help. ~ ÅÉAlt D - âÉMark the file for Delete. As above, if you have files selected , BRedit will prompt you whether or not you want to have all selected files marked. ~ ÅÉAlt F - âÉExtract File id. This will take the file id file out of the archive and import it as your new description for that file. Please note that it is VERY hard to comply with the standards set out for this file and the myriad of variations that we may have to encounter, so you may get the odd file that does not format properly, but you are free to edit it. ~ ÅÉAlt H - âÉHatch this File. You will be prompted if you have files selected as above. Also, you will be shown a list of areas where you may select which area you would like this file hatched into. You may hatch all selected files as well in a global format. ~ ÅÉAlt I - âÉInformation about this area. Such things as Days Old, FilBase,Add File, Del File etc. are all shown here to give you some basic info about this file area. ~ ÅÉAlt M - âÉMove File. Again, the prompt if you have files selected. As with Hatch and Copy, you will be shown a list of areas where you may choose the area to send this file to. Please note that the file AND the files record are moved. ~ ÅÉAlt N - âÉNo Kill, Marks the file as no kill making it absolutely invisible to the systems processing operations until it is cleared again either by the sysop or by the Utility programs No Kill feature. ~ ÅÉAlt O - âÉMark Ownership. This will redirect the file in its path to the destination area. In other words, if this file was destined to be in an area called "IBM_UTILS" and you alter it here, it may be in a totally different movement cycle. This is a VERY powerful feature and should be reviewed at great length in the documentation. As with most functions in the edit window, if you have selected files, you will be prompted to mark all of them with this ownership, giving you global capabilities. ~ ÅÉSpacebar - âÉSelects or "tags" current file. If you are moving your cursor in an up or down direction, BRedit will automatically "jump" to the next item, making it easier to simply flag files quickly by keeping the spacebar pressed. ~ ÅÉAlt T - âÉTouch File Date. This will reset the filedate in the database and update the file on disk to todays date. The file is only updated when you exit this base and this base is processed. If you choose to process this base, then the date will be updated. This gives you a chance to change your mind or to toggle it back to the original date. ~ ÅÉAlt V - âÉArchive Viewer. 6 Archive types are supported, ZIP, ZOO, ARJ, ARC PAK and LHA(or LHZ). The page will pause , showing you various info on each file. ~ ÅÉAlt X - âÉUnconditional Exit. This will not update the base nor change anything that has been edited but will immediately exit. This is to accomodate all you "pros". ~ ÅÉESC - âÉFinishes this bases processing. You will be prompted, if you had made changes to the base, to save the changes to disk , where you still have a chance to abort the changes. If you press "Y" the window will clear and BRedit will go into an uninterruptable processing mode going through various steps to process your edits. ~ ÅÉUParrow or LTarrow- âÉMoves the selection bar up one record. ~ ÅÉDNarrow or RTarrow- âÉMove the selection bar down one record. The screen will scroll if if you are on the bottom selection. ~ ÅÉHome - âÉIf you are NOT on the top item of the page, you will be taken to the top item on the page, otherwise , if you are on the top line , you will be taken to the first record of the database. ~ ÅÉEnd - âÉAs with above, if you are NOT on the bottom item of the current page, the selection bar is move to the bottom of the current page. If then you press End again, you will be on the last record of the current database. ~ ÅÉPage Up - âÉMoves up 15 records in the database. If you are on the first page then it takes you up to the top of the page. ~ ÅÉPage Dn - âÉAs with above, if you are on the bottom page, the selection bar is moved to the bottom item. If you are already there, then the bar is move to the bottom of the database. ~ ÅÉMouse Left Button - âÉButton to select, not abort, all selections. ~ ÅÉMouse Right Button- âÉAlways used to abort or back out of prompts/screens. ~ ÅÉTop Up Arrow - âÉYou will only see this if you have a mouse active. This arrow, when selected with the mouse left button will act in two steps. Just as the home key, this arrow will put you at the top of the page if you are currently not on the top of the page and will put you at the top of the file if you are already currently on the top of the page. ~ ÅÉBottom Up Arrow - âÉAs above, you will only see this when a mouse is active, this acts exactly as if the page up key were pressed. This will put you up 15 records from where you currently are. If that puts you to the top of the file, you are defaulted at first record. ~ ÅÉTop Down Arrow - âÉThis acts exactly as the page down key when the mouse is active. You will move down 15 records(a page) from your current location. If you are on the last page or not more than 15 from the bottom of the list, you will simply be put on the bottom of the list. ~ ÅÉSquare Box - âÉThis little solid gold colored box on the right hand box border is the same as pressing the Alt-X key combination. This would take you to DOS immediately and aborts any changes(except nokill, noshow and delete) you have made to the current list. ~ ÅÉAreas Selection Menu âÉ ~ Here you may choose the area you wish to edit. In editing you may move, copy delete, hatch or have two way file id handling. If you need further help in those areas, press F1 in the main edit window. ÅÉEdit Date ~ âÉHere you may edit the date of the file. The file on disk will also be updated if you choose to save the changes at the end of your editing session. ÅÉEdit Description ~ âÉHere you may edit the text of the description for this file. The changes will not be saved until you try to exit the editing at which time you will be prompted to save the changes. ÅÉMark All Files for Delete? ~ âÉThis is asking you if you would like to mark ALL of the selected(via spacebar or Alt S) files for delete? This gives you the global ability to flag files in a fast way. ÅÉMark All Selected for Abandon? ~ âÉThis is asking you if you would like to mark ALL the selected files as Abandon? When you abandon the file, you merely delete the record in the database, NOT delete the actual disk file. ÅÉMark All for Hatch? ~ âÉIf you press "Y" here you will have marked ALL selected files for hatch. After this, you will be asked to choose an area to hatch it to? ÅÉMark All Files for New Ownership? ~ âÉThis is a complicated option and you really should know about the file movement feature of Base Runner from the documentation first. Ownership is the recording of the file area that will be the final destination of the file. In other words, this area may move all files to another area, which in turn in a specified number of days, will move it to yet another until it finds its way to the destination directory where it will then stay. By altering this setting, you virtually change the "route" of this file. As with Copy or Move or Hatch, you will be prompted for the area to move this (or all marked) files to. ÅÉMark All Files for File Id Add? ~ âÉIf you press "Y" here, all the selected files will be processed with this feature. Here it will take the description of the file and insert it into the archive as a FILE_ID.DIZ file. This can ensure that all files on your system has a description in it. ÅÉMark All for File Id Extract? ~ âÉIf you press "Y" you will mark all selected files for File id extract. ~ File id extract is taking a file from the archive called "File_id.Diz", if it exists, and inserts it into your database for that file. File Id's are description files describing that particular file. ÅÉMark All Files for Copy? ~ âÉIf you press "Y" to this prompt, you will be marking all files for copy to another area. ~ By copying files rather than moving them, you will then have two copies of the file on your system. This may be desirable in some situations. ÅÉList Areas - Copy Files ~ âÉThis is a list of available areas on your system. Here you may select which area this (or all selected) file(s) will be copied to. Please remember that the original is not deleted, giving you two copies of the file and record. ÅÉMark All Files for Move? ~ âÉIf you press "Y" to this prompt, all selected files will be marked for move. ~ Moving the file will remove it totally from this area leaving the only copy of the file in that area. After this prompt you will see a list of areas to select from. ÅÉList Areas - Move Feature. ~ âÉThis is a list of areas where you may choose where to place the moved file(s) to. This movement won't actually happen until you exit this base. Then you will be prompted to make the changes or not. ÅÉMark All Files with New Ownership? ~ âÉThis will mark ALL selected files as having new ownership instead of just this one. Ownership is where you can tell Base Runner where to finally place the file in its route to it's destination. ÅÉClear All Entries Marked for File Id add? ~ âÉThis will clear all selected files from being set for File id Adds. File id Adds are the insertion of the existing description to the archive as a file called FILE_ID.DIZ. ÅÉClear All Selected Files of the Move Bit? ~ âÉThis tells Fbedit that you want to clear the file move tag from the selected files. If you do not use this, then only this file will be cleared. ÅÉClear All Selected Entries of the Delete Flag? ~ âÉThis removes the delete flag from ALL selected files rather than just this one. This makes the selections global. Deletions are when both the file and the database entry are deleted. ÅÉClear All Items Marked for Abandon? ~ âÉThis clears all selected files of having to be abandoned. This global feature allows you to globally unmark abandoned files. ÅÉClear All Selected Files From Being Hatched? ~ âÉInstead of just unflagging this file for a file hatch, you can unmark all selected files making this a global feature. ÅÉClear All Selected Files for Copy? ~ âÉThis will clear or unmark all selected files of having to be copied to another area, rather than just this file. ÅÉSave Changes? ~ âÉYes or No or Escape are the only inputs accepted. No or Escape will abort all changes made to the database and place you back into the main area selection menu. Pressing "Y" will put BRedit into the processing mode where it will make all the changes you made to the base. ÅÉDeletes Marked, Continue? ~ âÉBRedit has found deletions marked and wants to know if you would like to proceed. You can of course back out at the last second by pressing "N" here. ÅÉList Areas - Hatch Files ~ âÉHere you may select the area to hatch the file(s) to. If you selected more than one file then they will ALL be hatched to this area, otherwise just this file will be hatched. Page up or down as well as the arrow keys allow you to move freely about in the list, pressing enter will make the selection or escape will abort the function. ÅÉFile Areas - File Area NameâÉ ~ This field serves two purposes. Base Runner needs a unique name to identify each of your file areas so that it knows where to move files and so on. ~ This also serves as the file echo name. Like mail echoes, file echoes also have a unique name, as assigned by your Hub. If this is to be an area which echoes files to other systems, use the appropriate area name. ~ The area name can be up to 30 characters long, and MUST NOT contain any spaces. For example, NEW_FILES, SDN-PROG, CDROM3_IBM_UTILITIES, etc. ÅÉAutomatically Add Nodes not found in our Database?âÉ ~ This instructs Base Runner to Automatically insert a node entry for nodes not found there already. Their new entry will be added but will be rather sparse with info, you will have to complete the record at a conveniant time, but there is enough filled in for Base Runner to operate smoothly. ÅÉDebug for Above Settings? ~ âÉThis tells Base Runner to use ALL logging options regardless of the above settings. This way you don't have to lose the settings you had if you decide that you want them all for a short while to check out an error or some other info you may want to keep on your file handling. ÅÉLog Messageing Errors To Disk? ~ âÉIf there were any errors during message posting, setting this toggle to "Y" will allow you to see what those types of errors are, otherwise Base Runner will simply ignore the log entry. ÅÉLogging Levels/Options ~ âÉ Here you select the level of logging that Base Runner will use during various operations. You may also use the "Debug" option, which will use ALL levels regardless of other settings. ÅÉLog Regular System Messages to Disk? ~ âÉShould Base Runner be free and easy about its logging and include ALL messages it comes across? This is the most verbose listing available. ÅÉLog File Activity To Disk? ~ âÉBase Runner performs various disk file reads and writes and can notify you of these actions by setting this toggle to "Y". ÅÉLog Irregular Activity to Disk? ~ âÉThis would be that rare occurence that Base Runner does things it would normally not do such as move files etc. This setting allows that activity to be logged to disk. ÅÉLog Fatal Errors To Disk? ~ âÉThere are times when Base Runner, for whatever reason, cannot run under any circumstances with the current configuration. Setting this toggle to "Y" allows you to see what those types of errors were. ÅÉProcess User Uploads?âÉ ~ This tells Base Runner whether or not to import into its filebases any new user uploads that it finds. ÅÉFile Echo Area to Clone?âÉ ~ This tells Base Runner which Echo area to clone when auto creation is in place. Whenever a new area that is not recognized by Base Runner comes in, we can still process it, but we have to give it a new area. A new directory is created using the area name in the same sub directory as the clone record. ÅÉFile Area to Clone?âÉ ~ This tells Base Runner which File area to clone when auto creation is in place. Whenever a new area that is not recognized by Base Runner comes in, we can still process it, but we have to give it a new area. A new directory is created using the area name in the same sub directory as the clone record. ÅÉAuto Create Areas from this Node?âÉ ~ We can automatically clone an area, create a new sub dir and set up a new area for any non recognized area from this node if you so desire, but you have to have this toggle set up before it will operate. ÅÉPath to This Systems Work Directory?âÉ ~ Base Runner must have a seperate working directory for this node in order to maintain this nodes areas files to show to the user. These files are automatically updated while the requesting is going on. If the date is obsolete as reported by the requesting system, a new set of lists is attached as well, keeping the system constantly updated. ÅÉTheir System Name?âÉ ~ This is their system name as it will appear in BRFREQ, the online program. ÅÉTheir Security Level?âÉ ~ This is their assigned security level. It will be used when one of their users requests a file from us, each file areas security has to be lower than this number in order for this node to be able to access that particular area. ÅÉDoes this System Request files from you?âÉ ~ This tells us that this system is involved with us in a file requesting system. This is NOT the same as a FIDO file request, read documentation for more details. ÅÉBase to Place Incoming Files toâÉ ~ Here we may specify what file area to place this systems incomming files to. The area configuration for that particular area is what becomes the default for how those files are treated. For example, you now have the message base posting defaults for that area as well. ÅÉBytes this Node has taken from us TodayâÉ ~ This is the amount of bytes this node has requested from us today. This amount can be altered if you decide to clear off their stats for today and allow more requesting. This value represents all bytes this node has taken for the purpose of calculating their accounts and perhaps not giving them the file(s) based in this info. ÅÉFiles this Node has Requested TodayâÉ ~ The amount of files this node has taken. You may optionally edit this figure so that the node will still have to honor their limits. ÅÉAreas Not Found ~ âÉNumber of areas not found whenever this node requested am area via the areamgr. ÅÉFiles not Found ~ âÉFiles not found via the file/user requesting system. ÅÉDaily Bytes CapâÉ ~ The amount in bytes the requesting system is allowed to take per day. ÅÉDaily Files CapâÉ ~ The number of files this node is allowed to request per day. ÅÉUplink ListâÉ ~ This is the path and filename of the text file with the areas available from this node. If this node will not be configured as an uplink in the echo areas, there is no need to enter anything here, otherwise, this uplink will need a list specified. ÅÉDescription Options ~ ÅÉ"Y" âÉUses the file id file as the description for this file. ÅÉ"N" âÉUse the TIC's description lines as the new description. ÅÉUplink File Manager Name?âÉ ~ The Name that your uplink will recognize as a valid file manager name. For example, ALLFIX,DWTIC etc. ÅÉAdd File OperationsâÉ ~ Add Files is a plain text list with one line per file that will be added to the archive. The full path to the files to add must be in these path lines if the file is not in the current directory. ÅÉRequestable FlagâÉ ~ This tells us if this area may be included in the file request system. If you wish, you may have a full file request system but still limit exactly which areas are or aren't included. Set this to "Y" if you wish this area to be allowed to be requested from by other systems. Of course the other node would still have to have enough security to get access to this area, but this is more of a generic "Off" switch. ÅÉSecurity Required to Access this AreaâÉ ~ This is the security the node must have in order to request files from this area or to even have this area in their list at all!. If they DO have enough this area becomes visible to them and their users may then request and pull out files from your file area. ÅÉFile Areas - Description OptionâÉ ~ Compressed files usually contain a FILE_ID.DIZ, which is a text file that contains the file's description. Users usually add descriptions manually when they upload. .TIC files usually have the description within them. Usually. This option covers the unusual: ~ Never - Descriptions are never added, and assumed supplied.` Always - Descriptions are always imported from the FILE_ID.DIZ.` Needed - A description is added if missing from any of the above. ÅÉMessage Base to Place Request Announcements toâÉ ~ This is the message base to place the requested files announcement to. If blank, this will be ignored, otherwise when a new file comes in for a user, a message with the text specified under Msg Txt will be posted to the user to let them know their file has come in. ÅÉMessage Text File to use as Announcement Text?âÉ ~ This is the actual text that will be inserted and shown to the user. This can have any of the macros described under Echo announcements to spice up the info shown to the user. ÅÉEcho Area NameâÉ ~ This is the name of the echo area this area belongs to. This is a valid echo area and must be spelled exactly as it is coming in from your uplink or you will end up with auto echo created areas(if toggled) or you will not import anything at all. ÅÉEcho Area DescriptionâÉ ~ The description for this area is used usually for your own conveniance, to have a way of knowing what this area is about, but it is also used to generated downlink lists, so the comments in this field can also be seen by other sysops. ÅÉMessage Text for AnnouncementsâÉ ~ You can place any text you like into the message posted to announce this new file arrival. Please consult your documentation for all the available macros that you may put in this file. This is the path and name of the file holding the text(including possible macros) you wish to insert. If this is designated as an echo area in your PCB setup, you will also see Base Runners tag line appended to the bottom. ÅÉMessage Base for AnnouncementâÉ ~ This is the Echo Area tag for this area. The tag is a name for this area that will be used by your echomail tosser to place the message into the appropriate base. If you are running PCB, you must set up an area with this echo tag and tell PCB that the area is a Fidonet area. This way PCB will place the message into the proper area. Other systems behave according to the echo processor you are running at the time. Please consult the manual for the processor you are currently running for more details. ÅÉUploaded By: âÉ ~ You can use a macro in this line to show up the uploaded by field in your DIR files if you enter a valid line here. Please consult your documentation for more information on this feature. ÅÉOriginal Area to Place this File intoâÉ ~ The original area this file will be placed into. You can place files coming into this echo into any file area you like. Pressing enter will choose that areaname. ÅÉAlso Known As or AKA to useâÉ ~ This is one of your ten AKA's to use for this area. That will become the address you use to correspond to the nodes attached to that area, allowing multiple zones to be supported. ÅÉFile OwnershipâÉ ~ This is the area that the file will end up in. The file simply keeps moving from area to area until it reaches this area. When it reaches this area, it is considered to be "home" and will no longer move through the system. ÅÉPassthru Echo Area?âÉ ~ By default, Base Runner echos all files out in their original format and places a copy of them into the passthru directory. If you are not keeping the files for this area online, you can have it delete the attach from your system once all downlinks have it. ÅÉEcho Files Out from this Area?âÉ ~ A simple override to toggle absolutely no echoing from this area. This allows you to not have to remove all the downlink nodes from the list before it will stop echoing. This way you can put this area back "online" whenever you like, with one quick keystroke. ÅÉKeep Receipts for this Area?âÉ ~ This tells us whether or not you wish to have us save the netmail messages we sent out to nodes as responses to their file manager requests. ÅÉKeep RequestsâÉ ~ Should we keep other nodes file manager requests in netmail or delete them? If you want to keep them around so that you may monitor the activity and do not want to rely on the logs, then you can keep them and delete them manually. Setting this to "Y" allows you to do this. ÅÉFile Areas Global Menu Options ~ âÉ Convert - Allows you to toggle whether or not the areas in the folders you select will convert files to a default format for that area. You will be allowed to choose whether or not you wish to A)dd to existing bit masks or R)eplace the current set with this one or D)elete the options you selected(or turn them off).` Virus Scan - Toggles Virus Scanning for the specified areas.` Duplicate Check - Toggles Duplicate checking for the specified areas.` Keep Dates - Tells Base Runner to keep the original file dates when importing or moving files.` Strip High Ascii- Toggles the High Ascii filter for the specified areas.` Requestable - Makes the areaa either requestable or non requestable.` CDRom Area - Toggles whether or not the specified areas are CDRom drives and should not be written to.` Deletions - Toggles deletion(filebase entry but no DOS file) processing for the specified areas.` Orphans - Toggles File adoptions or "Orphan" checking for the specified areas.` Active - Toggles the "Active" flag for the specified areas but does not mark them for delete.` Uploads - Toggles whether or not Base Runner should process user uploads for the specified areas.` ÅÉEcho Area Global Menu ~ ÅÉAdd Node : âÉAllows you to globally add a node to a number of specified areas. You are prompted for a status bit(Receive,Send or Both) to set up the new node with and also the folders you wish to be affected by this change.` ÅÉDelete Node : âÉSimilar to above except that you will be deleting the node instead of adding it.` ÅÉChange Node : âÉAllows you to change the node number of a particular node in your areas. The node must exist already in the area before the change will have any affect. It cannot be used to add while changing.` ÅÉAka : âÉAllows you to select the Aka's you will use for the specified areas.` ÅÉInitial : âÉThis is the initial file area that files will go to when entering this echo area(the ones you will specify). After that, regular file movement routing will take effect.` ÅÉAnnoucement Echo : âÉThe echo area tag that will be used for file annoucements.` ÅÉOwner : âÉThe final destination point of the files that come into this echo area or owner. Ultimately, this area is where the file will wind up if all links are properly set up and are not set up to block movement in any way.` ÅÉOrigin Line : âÉThe default origin line to use in all selected areas. This applies to new file announcements only.` ÅÉAnnouncement File: âÉThe actual text file that will be used as a template for the message text in your announcemnts. If you do not use announcements, then this will have no effect.` ÅÉGlobal Toggles : âÉBreak down as follows...` ~ ÅÉPassthru` ÅÉEcho Area` ÅÉKeep Requests` ÅÉKeep Reciepts` ÅÉList Area` ÅÉDelete TIC` ÅÉDelete File` ÅÉNo Kill` ~ âÉThese can all be found in the documentation if you need to know what they do. Here you may globally turn on(Add),turn off(Delete) or replace(Replace) these settings. ÅÉInclude this Area in New Files Announcements?âÉ ~ Base Runner can announce new file arrivals by posting messages about it into your PCB message conferences. If you set this toggle to "Y" you are activating this feature. If this is "Y", you must still have a valid msg text file as well as a valid PCB MsgBase. F2 in the message base selection will allow you to view your PCB conferences. Please consult documentation for a more in depth look at Files Announcements. ÅÉDays to Keep? ~ âÉThis tells Base Runner how many days to hold onto the tics and file attaches for this node before deleting them. This will ensure that no one node clogs up your system with a backlog of files to go out. Any value between 0 and 65535 may be used here but please note that a setting of 0 tells Base Runner to keep the files indefinately(default). ÅÉDelete Tic Files after Processing?âÉ ~ This tells us whether or not you wish us to keep old processed TIC files around. Setting this to "Y" will tell us to clean them up and delete them after they are processed so this is usually set to "Y", but in some instance or if you wish to see what the file is(in case you are trying to figure out what is going wrong if that is the case) or some other info about the files, then this is the way to do it but remember, it may get awfully cluttered in your inbound directory. ÅÉDelete Inbound Attach Files?âÉ ~ You may wish to keep a copy of all incomming files in your inbound directory, in which case you would set this to "N" but usually, since you will still have a copy of it in whatever filebase it is going to, you would set this to "Y". ÅÉSecurity OptionsâÉ ~ This tells Base Runner to Keep this Area connected even if we have no downlinks. If you only have one uplink specified, Base Runner can automatically unlink you from this area, but if you want this area or if you are an end node, a setting of "Y" will ensure no disconnect. ÅÉFile Area Global Menu ~ ÅÉHatch To : âÉAllows you to specify what area files will get hatched to when auto adoptions are switched on.` ÅÉHeader : âÉAn optional header in your file areas may be inserted as well as a footer to customize your file areas. This global setting allows you to choose one header file to be used for many areas.` ÅÉFooter : âÉAs above, only this applies to the footer file, which is very similar to above, only it is tacked onto the end of the DIR file(or files.bbs) instead of the top. Please consult your documentation for more details on the operation of these features.` ÅÉAdd File : âÉAllows you to select a file to be inserted into all archives entering the area. If this pathname has a "%" as the first character, then it is treated as a text file containing a list of files to add to the archive.` ÅÉDelete File : âÉAs above, except that this time you are removing unwanted files or ads from the archives. Remember, these changes affect many areas at once. If you are unsure about the changes this feature will make, you may abort by pressing escape.` ÅÉComment File : âÉThe text file you wish inserted as the comment text. This global option allows you to insert one comment file as the default for many areas at once. If the first character is a "%" , then it is assumed to be a text file(supporting Base Runners macro system) otherwise it will be considered a one line comment.` ÅÉDelete by Age : âÉHere you may specify(in days) how long files will stay in the specified area(s).` ÅÉSecurity Level : âÉHere you may globally assign security levels to a folder of areas.` ÅÉDays Old : âÉSpecifies how many days before a file should be moved to its next area. Global setting here allows many areas to be affected at once.` ÅÉToggles : âÉThese break down as follows...` ~ ÅÉConvert` ÅÉVirus Scan` ÅÉDuplicate Checking` ÅÉKeep Original File Dates?` ÅÉHigh Ascii Filter?` ÅÉFile Requestable Area?` ÅÉCDRom Area` ÅÉDeletion Checking` ÅÉOrphan(Adoptions) Checking` ÅÉUpload Processing` ~ âÉThese can all be toggled in one of three ways. The first is to (D)elete or turn off the specified toggles in the specified areas. The second is to turn on or activate the toggles and the last is to replace the complete toggle set with the current one. As you can see, this affords the power to accomplish any task on a global level! ÅÉPaths/FilenamesâÉ ~ All the path and filename setup of the file requesting system for Base Runner. ÅÉOptions for the File Requesing SystemâÉ ~ Various settings may be altered here to suit your specific taste. This is strictly regarding file requesting and is not to be confused with system configuration. ÅÉBack to Main MenuâÉ ~ Returns you to the previous menu, in this case the Main interface menu. ÅÉPath/Filename of Intro ScreenâÉ ~ Fully qualified path and name of the file the user will first see when logging into the file requesting door. This screen may include regular PCB macros to enhance or customize the screen layout. ÅÉPath and Filename of Main MenuâÉ ~ This is the main functioning menu of BrFreq. It should perhaps contain the menu commands and any other info you feel you would like to show the user. Regular PCB macros will work in this or any of the file requesting systems screens. ÅÉPath and Filename of Bye ScreenâÉ ~ The last thing the user sees when coming out of the file requesting door. This may contain regular PCB macro codes and should contain any info you wish the user to see before exiting the door. ÅÉPath and Filename of Help FileâÉ ~ This is the path and filename of the file that will be shown to the user when they press "H" or "?" for help during BrFreq. This can include regular PCB macro codes to enhance your systems feel. ÅÉAre we File Requestable?âÉ ~ A system wide shut off valve for the file requesing system. If this is set to "N", then all input in the nodes database is shut off so don't be alarmed. As soon as you set it to "Y", they all reappear again. This is during the nodes dialogs. ÅÉDelete Sent File RequestsâÉ ~ This tells Base Runner about what you wish to do with requests generated on your system. If you set this to "Y" they will be deleted, if it is "N", they will be kept so that you may monitor them and delete them at your own choosing. ÅÉDelay after ScreensâÉ ~ 1000 milliseconds = one second. This allows for full control of the screens. If you have a lightning speed system, you may want to delay for a while so the user doesn' t just see this blur on the screen. A setting of about 400-600 is a good place to start and you can take it from there. ÅÉNode Number for Notify ListâÉ ~ This is a valid node number to send this notify list to. If you are unaware of what a node number is, please call your local Network req(eg, Fido, NANET etc) ÅÉMove Files after how many Days?âÉ ~ How long do we leave this file in this area before moving it? This tells us how many days to wait until we move it to this areas destination area. ÅÉAdd NodeâÉ ~ Adds a node to the downlink list of all the areas who belong to the folder you will have to specify. ÅÉDelete NodeâÉ ~ Takes out a node belonging to all areas of a certain folder(or group) which you will have to specify. ÅÉChange NodeâÉ ~ This will take a certain node number and change it to another node number. The number does not have to be in your nodes list but should be a valid fido node. ÅÉEcho Area Configuration Command Summary ~ ÅÉAlt-A - âÉAdds an area to the database. You will have to enter some information to properly configure the newly added area.~ ÅÉAlt-D - âÉDeletes a record from the database. Note that the record is not actually removed from the database, only disactivated. You will have to use Alt-P, Pack database if you want to remove the record permanently.~ ÅÉAlt-F - âÉFinds a record. Will automatically use the set search criteria for its search allowing multiple searches quickly and easily.ÅÉ~ ÅÉAlt-G - âÉGlobal Menu. Here you may do various things on a global level which can affect many records at once. This makes doing large edits a snap!~ ÅÉAlt-L - âÉConfigures the Downlinks/Uplinks for this areaÅÉ~ ÅÉAlt-P - âÉPacks the database. This will remove any records marked for delete permanently.~ ÅÉAlt-S - âÉSet Search Criteria. This lets you enter the search string for the next search.~ ÅÉAlt-X - âÉExit. Immediately exits the program, saving any database records first. ~ ÅÉCursor Movement and Selection Command Summary ~ ÅÉDnArrow or Right Arrow - éÉMoves the select bar down one item. If the select bar is at the bottom of the window, the window scrolls down one line.~ ÅÉUpArrow or Left Arrow - éÉMoves the selct bar up one item. If the select bar is at the top and you are not at the top of the file, the window scrolls up one line.~ ÅÉPage Down - éÉMoves the select bar down 15 items(or one page) if there are enough items left in the base, otherwise it will simply take you to the end of the list.~ ÅÉPage Up - éÉSame as above except in the upward direction.~ ÅÉControl Page Up - éÉSame as above except the increment is 2 pages or 30 items up.~ ÅÉControl Page Down - éÉSame as above except the increment is 2 pages or 30 items down.~ ÅÉHome - éÉThis works in two steps. One, if you are not currently on the top row of the window, you will be taken to the top of the window to the top row. If you are already at the top row, the next home key pressed will take you to the top of the list, no matter how many pages that is.~ ÅÉEnd - éÉThis works exactly the same as the Home key except that it moves in a downward direction.~ ÅÉEnter - éÉSelects the current area for editing. You will be taken into an open window where you may edit particular items for that area you are on.~ ÅÉFile Areas Command Summary ~ ÅÉAlt-A - âÉAdds an area to the database. You will have to enter some information to properly configure the newly added area.~ ÅÉAlt-D - âÉDeletes a record from the database. Note that the record is not actually removed from the database, only disactivated. You will have to use Alt-P, Pack database if you want to remove the record permanently.~ ÅÉAlt-F - âÉFinds a record. Will automatically use the set search criteria for its search allowing multiple searches quickly and easily.ÅÉ~ ÅÉAlt-I - âÉImport from PCB. Here you may select any areas you wish Base Runner to import. Base Runner will scan through PCB's area configuration, listing only the areas you do not already have in your database. We decide this by checking the destination path of your DIR.LST files and if we already have that directory under our control, we assume it is an area you do not need to see. Once you have selected the areas with the spacebar you wish to import, press ESCAPE and you will be prompted to go ahead with the import. If you press enter or "Y", you will see how many changes are made on the bottom status line of your screen. Press any key to Continue and your screen is refreshed with your newly created areas. Base Runner tries its best to fill out these areas with as much information as possible, but you will still be required to go in and edit them to make sure they are properly configured. This is due to the simplicity of PCB's DIR.LST files, we can only obtain a certain amount of information.~ ÅÉAlt-L - âÉLinks Information and Input for LInks.ÅÉ~ ÅÉAlt-P - âÉPacks the database. This will remove any records marked for delete permanently.~ ÅÉAlt-S - âÉSet Search Criteria. This lets you enter the search string for the next search.~ ÅÉAlt-X - âÉExit. Immediately exits the program, saving any database records first.~ ÅÉCursor Movement and Selection Command Summary ~ ÅÉDnArrow or Right Arrow - éÉMoves the select bar down one item. If the select bar is at the bottom of the window, the window scrolls down one line.~ ÅÉUpArrow or Left Arrow - éÉMoves the selct bar up one item. If the select bar is at the top and you are not at the top of the file, the window scrolls up one line.~ ÅÉPage Down - éÉMoves the select bar down 15 items(or one page) if there are enough items left in the base, otherwise it will simply take you to the end of the list.~ ÅÉPage Up - éÉSame as above except in the upward direction.~ ÅÉControl Page Up - éÉSame as above except the increment is 2 pages or 30 items up.~ ÅÉControl Page Down - éÉSame as above except the increment is 2 pages or 30 items down.~ ÅÉHome - éÉThis works in two steps. One, if you are not currently on the top row of the window, you will be taken to the top of the window to the top row. If you are already at the top row, the next home key pressed will take you to the top of the list, no matter how many pages that is.~ ÅÉEnd - éÉThis works exactly the same as the Home key except that it moves in a downward direction.` ÅÉEnter - éÉSelects the current area for editing. You will be taken into an open window where you may edit particular items for that area you are on.~ ÅÉSelect Origin Line to Use ~ âÉSimply move the cursor keys around, page down, home, end, all the positioning keys work. When you are on top of the origin line you wish to use, press enter. Escape will abort and restore the original origin line. ~ These origin lines will be appended to message announcements when new files come into the system with announcements toggled on for this area. PCB codes are also supported but only while in PCB, other systems may not wish to see your translated codes, so use the PCB codes sparingly. ÅÉNodes Command Summary ~ ÅÉAlt-A - âÉAdds an area to the database. You will have to enter some information to properly configure the newly added area.~ ÅÉAlt-D - âÉDeletes a record from the database. Note that the record is not actually removed from the database, only disactivated. You will have to use Alt-P, Pack database if you want to remove the record permanently.~ ÅÉAlt-F - âÉFinds a record. Will automatically use the set search criteria for its search allowing multiple searches quickly and easily.ÅÉ~ ÅÉAlt-P - âÉPacks the database. This will remove any records marked for delete permanently.~ ÅÉAlt-S - âÉSet Search Criteria. This lets you enter the search string for the next search.~ ÅÉAlt-X - âÉExit. Immediately exits the program, saving any database records first.~ ÅÉCursor Movement and Selection Command Summary ~ ÅÉDnArrow or Right Arrow - éÉMoves the select bar down one item. If the select bar is at the bottom of the window, the window scrolls down one line.~ ÅÉUpArrow or Left Arrow - éÉMoves the selct bar up one item. If the select bar is at the top and you are not at the top of the file, the window scrolls up one line.~ ÅÉPage Down - éÉMoves the select bar down 15 items(or one page) if there are enough items left in the base, otherwise it will simply take you to the end of the list.~ ÅÉPage Up - éÉSame as above except in the upward direction.~ ÅÉControl Page Up - éÉSame as above except the increment is 2 pages or 30 items up.~ ÅÉControl Page Down - éÉSame as above except the increment is 2 pages or 30 items down.~ ÅÉHome - éÉThis works in two steps. One, if you are not currently on the top row of the window, you will be taken to the top of the window to the top row. If you are already at the top row, the next home key pressed will take you to the top of the list, no matter how many pages that is.~ ÅÉEnd - éÉThis works exactly the same as the Home key except that it moves in a downward direction.` ÅÉEnter - éÉSelects the current area for editing. You will be taken into an open window where you may edit particular items for that area you are on.~ ÅÉMark all Files or just this One? ~ âÉBrEdit is asking you if you would like to toggle all of the selected files as No Show or just this one. If you answer "Y" to this, all files will be marked and the selected flags will disappear from the marked files. ÅÉDelay how many days between list updates? ~ âÉSome nodes may be connected long distance or may just not want updates every single time the other system refreshes their file areas, which on a busy system can be dozens of times per day. If you leave this at zero, there will be no delay in updating. If you set this to a value higher than zero, then the other system will get their lists at this minimum interval each time. ÅÉPath and Name of your TrashCan File ~ ÅÉNew Files from Echos` âÉThis is now considered the trashcan for new files coming into the system. Here you place one filename per line, wildcards accepted, no path, into this file of the filenames you wish NOT entered into your system. If "Move to bad" dir is enabled for the particular area this file is trying to enter into, then the file will be moved to your BAD_FILES area, otherwise it is ignored and left in your inbound until you deal with it yourself. Please note that this does NOT apply to echoed files and that if a file is coming into an echo area that downlinks files, the file still goes out as usual. This ONLY applies to file areas, not fileechos. So, your resulting trashcan file might take on this type of appearance if you were using it for both nodes and files...~ ÅÉAMI*.ZIP` ÅÉFIDOLIST.*` ~ ÅÉPCB Style or *.MSG style Netmail Handling? ~ âÉThis tells Base Runner which way to handle netmail attaches. Answering "Y" to this question tells us you wish to use PCB style netmail handling. When using PCB style, the editing field for netmail path becomes the actual path to the MSGS file of your netmail conference. If you can't remember the path and name, press F2 here and if this machine has a PCB envoironment variable set up it will load up all your PCB conferences and let you select from a list by pressing enter on the conference listing you wish to use. Please note that NETMAIL is hard coded for PCB's netmail conference so please use that area to comply with PCB's configurations. The other way is to have a valid path in the pathnames/path to netmail dir field to your *.MSG type Fido netmail directory, the same one your Front Door or D'Bridge or ANY type of mailer that uses this type of *.MSG handling. This way you have more flexibility with the use of your front end while using Base Runner. ÅÉAlternate Address to send files to ~ âÉ This is an alternate address to route this nodes files to. This may be a temporary setup where you would like to process a nodes files while they are away or for whatever reason, you might like to route to an alternate address. ÅÉBytes In ~ âÉThis is the total Bytes you have received from this node. ÅÉFiles In ~ âÉThis represents the total files you have received from this node. This number, if reset, will then no longer reflect the true number processed by this node. ÅÉBytes Out ~ âÉThe total bytes sent to this node. ÅÉFiles Out ~ âÉThis is the total files you have sent this node. ÅÉFile Cap ~ âÉThis is a value, in kilobytes, that you may set as the total number of files this node can receive from you. Once this value is reached, no more files will be sent until it this value is altered to allow it. ÅÉByte Cap ~ âÉThis is an optional toggle allowing you to set the bytes this node is allowed to take. This is handy for pay systems. ÅÉPath to Uplink lists ~ âÉDOS path to where you would like Base Runner to keep Uplinks lists. ÅÉAuto Uplinking Operations? ~ âÉThis tells us whether you would like Base Runner to automatically scan your nodes lists to see if they have any text lists with file areas in them. If they are valid areas and the requesting node has access to the proper folder, then we request the area from that uplink and create a new area with both the uplinks address and the new downlinks address as links to that area. ÅÉAuto Hatching? ~ âÉYou already have area per area control over whether you would like to perform auto-hatching(adoptions) but this is a nice way of toggling it off system wide WITHOUT losing the present settings for your areas. Remembering which areas were on when you decide to come back to using it on an area per area basis is as simple as toggling this off again. ÅÉExport Data ~ âÉThis allows you to export to a disk file(or PRN for printer) certain configuration/nodes data you may wish to use. A particularily useful item on this list is AREAS.BBS. Although this file type is commonly used in echomail systems, the format is very useful for other things such as a quick reference point for nodes, downlinks etc... ÅÉPath to your Nodes Trashcan File ~ âÉThis tells us where to look for the file that contains node numbers, one per line, of the nodes you wish NOT connected in any way. This means you must have autonodes set or it will have no effect. This is unlike the regular trashcan which deals only with files and not node addresses. Unfortunately, since we do not maintain a nodelist at all and have no static way of knowing just WHO you mean by specifying a wildcard node number ,wildcards are not permitted. ÅÉPath/Name of RA Directory ~ âÉThe path and name of the FILES directory. This is the directory with the three subdirectories in it called TXT,HDR and IDX. From this directory Base Runner can easily find all of Remote Access' file areas. ÅÉNet Out? ~ âÉThis is an alternate path to outbound netmail attaches. You still MUST have an inbound netmail directory for inbound messages. If this has a valid path, it is used for attaches instead of the netmail directory. If it is left blank, then the regular netmail directory is used(Default). This is useful in some cases where the front end sending out the files is not the same as the machine bringing in the files. This is quite helpful for large hubs who process across their networks. ÅÉSelect Echo Areas ~ âÉThis is a dialog box with a list of echo areas that are on your system. For most prompts, these areas should be only one way to enter area names. You can also enter the area name yourself if it is not in your list(this would apply in a case of announcements where ANY area may be used, not just ones in your database). This ensures a full range of names being able to be used. ÅÉSelect Echo Areas ~ âÉThis is a dialog box with a list of File areas that are on your system. ÅÉVirus Scanners Successful Exit Errorlevel ~ âÉThere are a myriad of virus scanners out there these days. With that you get a wide variety of errorlevels that the program exits with depending on its status or whether or not it found a virus. We are not concerned too much with what the errorlevels are except for one. The successful exit. It is usually zero but any number from 0-255 may be entered. You may have to consult your virus scanners manual for details on your particular virus scanner. ÅÉDays to Keep History Lists ~ âÉThis tells us how many days of history records should be kept in the history file. This file is handy for generating bulletins via the utility program or for simply monitoring the recent activity on your system(s). ÅÉFiles In ~ âÉThis is the total files that have gone through this echo area. This does not include hatched files. To calculate total of the area, you must add the number of hatched files as well. ÅÉFiles Out ~ âÉNumber of files that have gone out through this echoarea. This number does not include hatched files but does include every downlink as one copy of the file. If you want total files you must add this number with the hatched files out. ÅÉBytes In ~ âÉTotal bytes less hatched bytes that this echoarea has had traval through it. ÅÉBytes Out ~ âÉTotal bytes less hatched bytes that this echoarea has had travel through it. ÅÉHatched Files ~ âÉTotal number of hatched files through this echoarea by your system. ÅÉHatched Bytes ~ âÉTotal number of bytes that have been hatched through this echoarea by your system. ÅÉReports Menu ~ ÅÉMain Configuration - âÉBase Runners main configuration may be exported to a âÉtext file of your choosing. You will be prompted for the filename. This applies to all the reports menu items in this help topic(filename). Such topics as your akas,main paths,compression info,origin lines etc are included in this general all purpose report. By specifying PRN or LPT1 or LPT2 as the filename , you may print the report.~ ÅÉOne Nodes Configuration - âÉOnes nodes connections are reported in a files.bbs style listing.~ ÅÉAreas in Folder - âÉThis will give you a report of all areas that belong to a certain folder(or group) as well as its description.~ ÅÉAreas.Bbs - âÉAn areas.bbs style listing of all your areas with all your downlinks for each area.~ ÅÉHistory - âÉThis VERY detailed report will tell you how many files have come in, how many have gone out, how many have been hatched as well as a myriad of other info, for example... was it virus scanned, was it imported, was it recommented, were files added, were files deleted, was a file id file inserted etc. Each file is listed and includes only the days back from this date that your configuration specifies under system info->global options-> history days.~ ÅÉAka ~ âÉHere you may select the akas that will be used for the folders you choose. They will become the new akas and will be written to disk. ÅÉInitial Area ~ âÉThis will set up all areas in the folder you select to point to this one initial file area. The initial field is used to "connect" the echo area to a particular file area so that they may work together to form your files system. This areaname is the area that all files processed from this echo will go into. ÅÉMessage Base ~ âÉThis is the echo tag used for announcements when echoing files into this echo area. This global option allows you to set up and make all areas in a set of folders point to one such "tag" or echoname. @15,0Owner ~ âÉOwnership is the file area that a file will end up in as its final destination point. The area is said to "own" the file. A file may take quite some time to get there, however, as it may have to filter through all the other areas it was linked to(from initial to its link etc) and moved through. This is an easy way to set ownership to an area for many file areas as it is possible to have many echos send their files to a single file area (crossposting). ÅÉOrigin Line ~ âÉWhen a file is announced into an echo, a message is generated and a custom origin line may be used. You may wish to use one origin line for many areas that are all in the same folder. This way you can do that in one quick and easy step with this global Origin Line option. ÅÉAnnouncement File ~ âÉThis is the text file that is inserted as the text of the message that will be announced. It may contain special macros to help in customizing the posted message. Please read the documentation for more details on these macros. This global option allows you to set up all areas in the selected folders to use this one file. ÅÉRequested files from this Node ~ âÉThis is the number of files this node has requested from us. This number is not reflected in the total echo files in but is calculated at the top of this window as you changed the values. ÅÉBytes In from File Requests/User Requests ~ âÉNumber of bytes from this node via file/user requests, not echoed in. ÅÉBytes To this Node ~ âÉBytes to this node via requests. This value is not the same as echo bytes in. ÅÉFiles sent out by file request to this Node ~ âÉThe number of files this has taken from us via file request. ÅÉViolations ~ âÉNumber of times this node has exceeded their ratio in any way. This value includes any caps which were exceeded. ÅÉNotify? ~ âÉNotify lists are messages (netmail) that are sent out to the nodes specified in the nodes database. Theses messages include echo connection information as well as other system info that the node may use for such things as comparing it to their own lists to see if there are any dead areas. ÅÉScreen Blanker Delay? ~ âÉBREdit has a built in screen blanker which will dim your screen until you either press a key or press the left mouse button(if you have a mouse installed). This saves your screen from "Burn in". This field accepts the number of minutes of inactivity before the blanker is invoked. ÅÉName of External Editor ~ âÉThis is the name and extension of the program you wish to use for external edits. We have used quite a few successfully but you may have to experiment to find one that does not use up too much memory or does not take the filename to be edited on the command line. Base Runner passes the program name and the file name to the program to be shelled to. After saving this file the edits are immediate. In BREDIT, you may use this by pressing F2 in the edit window on the current selection instead of pressing enter to use the default editor. There is no other default editor for BRCONFIG.~ ÅÉProcess User Uploads? ~ âÉBase Runner has the abiltity to import user uploads directly into the filebase. This makes the BBS interface even more seamless. Because most BBS packages offer a VERY extensive uploading module, Base Runner does not get into any great detail when importing these files. The reason for this is that the BBS has already done the processing on the file just as you would have wanted it(An very fine Upload processor by the name of SpotChek is available through CompuData Systems), so why process the file to death? ~ âÉWhen this toggle is set to "Y", Base Runner will check the validity of the archive by reading in the headers and matching the specs found with the actual file statistics. If this is satisfied, a 3 level duplicate check is performed, the first level being the CRC value of the file itself, byte by byte, the second being a CRC value of the area the file is going into and the third is a CRC value of the name of the file. The description options for this area are honored and the file id file will be used instead of the description(Please consult documentation under File id Opts). Three possibilities are presented here with regard to the file id files. If you selected Never under file id options, the file id file will never be created using the BBS description. Selecting Always will ensure that the BBS description is always inserted as the new file id file. Selecting Needed tells Base Runner to add a new file id file from the BBS(user upload description) description only if no file id file currently exists in the archive. After all this is done, the file is added to the file area but NO new DIR(or FILES.BBS) file is generated. ÅÉHTML Bulletins? ~ âÉThis tells Base Runner you wish to create HTML style bulletins. These are bulletins that have special strings in them so that HTML servers(Internet World Wide Web uses this all the time) can parse them and set up such things as font sizes, titles, lists etc. In text mode, this would actually make it look unlegible, but the HTML server knows just what to do with it. If you do not intend to put these reports onto the Internet, you may set this to "N", otherwise, set it to "Y". ÅÉUpdate Magic List? ~ âÉMost front ends maintain a "Magic List", a list of alias names to send when a magic name is offered as a file request. As well as maintaining this list for your front end, it may be used by BR as well to offer its own magic lists. BR maintains the "standard" and complies to all FTSC standards for this list so you will have no problem interfacing this list with your current front end. ÅÉReplaces which filename? ~ âÉThis tells us which filename you wish to replace with this one you are now hatching. If you input a filename here, the remote system(if it is compliant with the standards) should replace this file with the one you are now hatching. Not all systems adhere to this standard, however and are not considered to be FTSC compliant. ÅÉPath and Name of Magic List ~ âÉA magic list is a list of "aliases" for files, so to speak. It is just a text file with some file translations so that if your front end uses or supports magic filenames(as Base Runners request system does), this list will be automatically updated as new files come in or requests come in. This may be any qualified DOS path and filename. Pressing F2(if external text editor is specified) will allow you to directly edit this file from here. ÅÉPath to Embedded Directory ~ âÉBase Runner will process embedded archives, archives within archives so that your virus scanner can be more complete in checking for virus'. This temporary directory is where these files will be extracted to, if any exist. ÅÉMinimum Disk Space ~ âÉThis is the default minimum disk space on destination drives. This number must be lower than the current available disk space in order for ANY imports or moves can be performed and is calculate in Kilobytes, not bytes. As an example, the default of 5000 represents 5 megs of disk space, so if there was only 4.3 meg free, that particular operation would not be performed until you clear up some drive space. ÅÉNumber of Bad Password Violations ~ âÉNumber of times this node has used a bad password for areamgr operations. ÅÉHatch Master List to which Echo? ~ âÉBase Runner will hatch out the master filelist to an area. That areas downlinks will automatically get the list. You may disable this feature by leaving the field blank. ÅÉList CDROM Drive Letters ~ âÉA list of drive letters that are CDROMS. These drives will be ignored by any disk I/O requests as well as minimum drive space management. ~ Enter all the letters of the drives as they are mapped out with no spaces... ~ Example DGI ~ Would mean that drives "D", "G" and "I" are all CD Rom drives. ÅÉPCB Conference Configuration? ~ âÉThis is the conference you wish to have updated when this node invokes the autoadd feature. What this means is that when this node has autoadded an area, the status is checked to see if you are running a PcBoard system. If you are, then this conference is the conference that the new info is added to. ~ âÉTo go into a little more detail, There are two files that are affected by this. One is your DLPATH.LST file, the file that holds all the paths that are downloadable in that conference. The other is the DIR.LST file, a file that has only the file area listings in them(when you are PcBFiler and press F2 to see the descriptions of the areas, for example). Each of these files are appended with the new information. The path is added as a newly downloadble path and the area gets a new file listing added to it. ~ âÉSorry, at this time, we cannot modify your actual DIR file, the screen file shown to users when they wish to see your file areas, because we really can't tell what format you have it in, specially with your graphics layout. This you will have to add yourself, but it should make things a little easier now that the config is already there for you. ÅÉAnnounce Packet Directory ~ âÉThis is the directory where the announcements are written to in .PKT form. If this field is left blank, the regular inbound directory is used by default, otherwise the PKT files will be placed in this directory. ÅÉFile Folder Editing ~ âÉThese are the groups of areas collected together to form a similar activity while using global edits as well as access for nodes to certain areas. You simply give one of these folders a name and then later on you may use them to allow access for areas that belong to this folder. As an example. ~ ~ ÅÉFido ~ âÉ...may be the general Fido echo areas. With this certain nodes may be allowed access to this folder(in nodes editing) while others may not, effectively restricting access to the areas belonging to this folder. You may also create folders that are seperate from these to denote manipulation of BBS areas, which are seperate from access and from the folders found in TIC areas. In this case, you may limit access to certain BBS areas by making sure the specified node does not have access to this folder. The third use for these is to simply group together similar areas for ease of use for global operations, found both in TIC and BBS areas. ÅÉPick Folder ~ âÉSelect the folder you wish this area to belong to. Pressing escape will default the value back to what it was originally as if you had aborted it, otherwise pressing enter on the field you want will alter its value. ÅÉArrival Date ~ âÉUnlike the date field above this one, which is for both the file date on disk and the date of the file in the database, this field manipulates the date that the file arrived into this area. This is useful for file movement where you may wish to move the date "back" in an effort to have the file move on an earlier date than is the characteristic for this area, but not have to "restamp" the files date or change the movement days in your setup. ÅÉLogType ~ âÉThis allows you to select the style of log you wish to have Base Runner use. There are many styles to choose from. ÅÉVideo Mode ~ âÉThere are 3 available video modes ~ ÅÉQuiet âÉ- Runs in flat ascii mode or stdout mode.~ ÅÉEga âÉ- Runs the main program in ega 16 color mode.~ ÅÉVga âÉ- Complete palettes, special fonts, Vga mode.~ âÉThis allows you full control for the envoironment you are in. In either the Ega or Vga modes, they are fully Desqview aware and write directly to the calculated screen buffers, whereas the Quiet mode does not directly write to the screen. This info is required for filling in the Desqview defaults. ÅÉAdvanced Tic Files? ~ âÉSome TIC processors cannot parse or do not need to have an advanced tic file created, or they may read the tic file in a particular order that is congruent with the older style. Base Runner, for example, makes full use of advanced TICS(make sure your uplinks are sending you advanced Tics). These are tics which do not support such fields as "LDesc","Cost" or "To". ÅÉTic Mode ~ âÉThis is the mode this node wishes to receive their tic files in... ~ ÅÉNone : âÉNo TIC file attached, file is sent only.~ ÅÉTics : âÉTic file attached to file, not packed.~ ÅÉPack : âÉTic files are packed into an archive.~ ~ Downlinks which support the packed tic format may then recieve less files and attaches resulting in a shorter transfer time. ÅÉCompression Format? ~ âÉAll the regular compression formats that your system uses can be plugged into the nodes compression formats as well. This allows you to offer any of your existing compression program formats to your downlinks so that they may recieve their files and(?) TICS in one archive compressed in this format. ÅÉMaximum Archive Size ~ âÉBase Runner can limit the size of the outbound archives to a certain ceiling. As a rule, however, Base Runner will not add to an archive larger than 32 Megs, but this setting can be anything up to 65535Kb. A setting of zero tells Base Runner not to limit the size.
